[release-1.35] integration tests: switch some base images #5814
Conversation
Replace some of the base images we've been using (particularly centos:8, which will EOL soon) with other images hosted on quay.io. We already use registries.conf at test-time to redirect some image references there, so this will slightly reduce the number of registries which we need to be able to reach while running these tests. Signed-off-by: Nalin Dahyabhai <[email protected]>
openshift-ci
bot
added
the
kind/failing-test
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nalind The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Ephemeral COPR build failed. @containers/packit-build please check. |
|
/label jira |
|
@nalind: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
nalind
added
the
jira
CentOS and RHEL are moving to 1.37, so we don't need to try to build for them (or EOL Fedora releases) when we know those attempts will fail. Signed-off-by: Nalin Dahyabhai <[email protected]>
nalind
force-pushed
the
integration-base-images-1.35
branch
from
58baf5c to
e3da2cf
Compare
|
Changes LGTM |
|
Assuming it's up to date, the bottom of https://fedorapeople.org/groups/schedule/f-39/f-39-all-tasks.html notes that Fedora 39's end-of-life date will be less than a week from now. |
|
A friendly reminder that this PR had no activity for 30 days. |
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
Replace some of the base images we've been using (particularly centos:8, which will EOL soon) with other images hosted on quay.io.
We already use registries.conf at test-time to redirect some image references there, so this will slightly reduce the number of registries which we need to be able to reach while running these tests.
Manually cherry-picked from #5499 to resolve conflicts.
How to verify it
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
Does this PR introduce a user-facing change?